Modifying Tasks at Runtime

When an object is manually modified and stored, the system checks whether it is currently being executed and, if so, displays a message prompting the user to confirm the changes. The reason is that usually, runtime changes affect the ongoing execution. The following modifications show little or no effect:

Object type

Modified setting

Effects

All executable objects

Start type (Group)

None

Note: The GET_ATT script function provides the name of the new group.

Notification

Responsible recipient, calendar and calendar event

None

Event

Calendar tab

None

File Transfer

Use of wildcards

None

Job

Host

No effect when the job is in the status Waiting for agent.

Workflow

Content of the Workflow page

None

Properties of tasks

Modifications only take effect if made via the Workflow Monitor

RemoteTaskManager

Filter specifications

None

Schedule

Period and result evaluation

None

Content of the Schedule page and properties of tasks

Modifications take effect if made in the monitor. If made in the object, a message prompts you to confirm whether the changes should be reloaded at the next period turnaround.

See also:

Working with Tasks